Docs: Add fix to suggested prefixes of branch #30953
Conversation
|
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @arthur791004! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
github-actions
bot
added
the
First-time Contributor
kevin940726
added
the
[Type] Developer Documentation
There was a problem hiding this comment.
We've already been using the fix/ prefix a lot internally, I think it makes sense to include it in the doc to recommend using it for contributors.
|
Congratulations on your first merged pull request, @arthur791004! We'd like to credit you for your contribution in the post announcing the next WordPress release, but we can't find a WordPress.org profile associated with your GitHub account. When you have a moment, visit the following URL and click "link your GitHub account" under "GitHub Username" to link your accounts: https://profiles.wordpress.org/me/profile/edit/ And if you don't have a WordPress.org account, you can create one on this page: https://login.wordpress.org/register Kudos! |
Description
I'm reading git-workflow of Contributing Guidelines and I find that there aren't suggested prefixes of branch name related to fix an issue. Therefore, I add
fix/prefixes to the docsTypes of changes
Documentation